Summary

KeyborgProps was the only argument to createKeyborg/createKeyborgCore, gating two opt-in features:

• triggerKeys — a custom set of key codes that should enter keyboard-navigation mode in place of the default predicate (any non-Tab key on a non-editable element). No known consumer passes a custom set; the default already covers screen-reader and Tab-driven flows.
• dismissKeys — a key set that scheduled a 500 ms timer to dismiss keyboard mode if focus did not move (typically wired to Escape). This hand-rolled latch duplicated work consumers already do at the application level.

Drops:

• the KeyborgProps interface,
• the triggerKeys / dismissKeys Set construction,
• shouldDismiss / scheduleDismiss / dismissTimer / _dismissTimeout,
• the triggerKeys membership check in shouldTrigger,
• the dismiss-timer cleanup branch in dispose.

onKeyDown collapses to a single guard:

const onKeyDown = (e: KeyboardEvent): void => {
  if (!isNavigating && shouldTrigger(e)) {
    setNavigating(true);
  }
};

Public API impact

• createKeyborg(win, props?) → createKeyborg(win).
• KeyborgProps type is removed.

KeyborgProps was never re-exported from src/index.mts, so it was only reachable via deep imports. Callers passing the second argument hit a type error; callers passing nothing are unaffected. Worth a minor or major bump depending on how strict the maintainers want to be.

🤖 Generated with Claude Code